A.1. Truncation
In an ideal scenario all servers and all mobile devices would store their calendar data as iCalendar and they would support all attributes that iCalendar supports and would support attribute values of any length. Given the inherit restrictions of memory and storage prevalent with most mobile devices this utopian vision however is a rarity.
More then likely (although this is changing as mobile devices become more and more sophisticated) the device may only be able to expose a subset of the information possible from the desktop application and certain attribute values may need to be truncated. This is acceptable as long as an adequately accurate representation of the event is still available to the calendar user and if such restrictions do not end up adversely effecting the original server-side representation.
A user creates a meeting with a start time, duration, title, and some details. The calendar application on the device the user uses can only display start time, duration, and title. If the user modifies the start time from the device and then synchronizes the details should not be lost on the server-side representation of the event.
A user creates a meeting with a start time, duration, title, and a long description of the agenda. The calendar application on the device the user uses can display the start time, the duration, the title, and some details but it is limited to an amount of characters less then the length of the agenda so the entire agenda cannot be seen by the user from the device. If the user modifies the start time from the device and then synchronizes the agenda should not get truncated server-side.